Terminal and communication method of the same

ABSTRACT

The present invention relates to a terminal and a communication method of the same. According to an embodiment of the present invention, a communication method of a remote terminal may include: transmitting, to a relay terminal, a request message comprising ProSe (proximity based service) per-packet priority associated with a TMGI (temporary mobile group identity); and receiving, from the relay terminal, a MBMS traffic transmitted based on the ProSe per-packet priority.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/231,663 filed on Aug. 8, 2016, which is related to andclaims priority under 35 U.S.C. § 119(a) to U.S. Patent Application No.62/202,406 filed on Aug. 7, 2015, the disclosures of which are hereinincorporated by reference in their entirety.

BACKGROUND 1. Field

Various embodiment of the present invention relate to a terminal and acommunication method of the same.

2. Description of Related Art

Generally, a mobile communication system has been developed to providecommunication while securing mobility of a user. The mobilecommunication system may provide a voice communication service and ahigh-speed data communication service by virtue of the rapid progress oftechnologies.

In recent years, as one of the next-generation mobile communicationsystems, standardization for a long term evolution (LTE) system in 3rdgeneration partnership project (3GPP) is in progress. The LTE system hasbeen developed to be commercialized by 2010 and is a technology ofimplementing high-speed packet based communications having atransmission rate up to 100 Mbps higher than a data transmission ratenow being provided and the standardization for the LTE system is almostcomplete currently.

Meanwhile, the Internet is evolved to an Internet of Things (IoT)network that transmits and receives information, such as things, betweendistributed components and processes the information, in ahuman-centered connection network on which human generates and consumesinformation. The Internet of everything (IoE) technology in which thebig data processing technology, etc., by connection with a cloud server,etc., is combined with the IoT technology has also emerged. To implementthe IoT, technology elements, such as a sensing technology, a wired andwireless communication and network infrastructure, a service interfacetechnology, and a security technology, have been required. Recently,technologies, such as a sensor network for connection between things,machine to machine (M2M), and machine type communication (MTC), havebeen researched.

In the IoT environment, an intelligent Internet technology (IT) servicethat creates a new value in human life by collecting and analyzing datagenerated in the connected things may be provided. The IoT may beapplied to fields, such as a smart home, a smart building, a smart city,a smart car or a connected car, a smart grid, a health care, smartappliances, and an advanced healthcare service by fusing and combiningthe existing information technology (IT) with various industries.

The IoT technology has been in limelight in various fields and carriersand vendors have developed several applications and systems using theIoT. Among various IoT solutions, in particular, a cellular IoT(hereinafter, ‘CIoT’) using a licensed frequency band allocated to thecellular system has been in limelight. The cellular system may providerelatively more reliable communication than a non-cellular system,thereby providing the reliable service. In connection with the CIoT, thestandardization activities of evolved machine type communication (eMTC),global system for mobile communications enhanced data rates for GSMevolution radio access network (GERAN) CloT, etc., have been activelyprogressed and in characteristics of the standardization activities, aneed of carriers often has a crucial effect on a standard determination.

The evolved communication technology may provide communications betweenall things as well as between users, which is expressed by the term‘Internet of Things (IoT)”. For example, a user may have various kindsof electronic devices. All the electronic devices are connected to eachother by a mobile communication or local area communication technology,various sensors, etc., such that it is possible to provide moreconvenient functions to the user or perform an efficient control betweenthe devices. The electronic devices may be collectively called an IoTdevice. An example of another IoT service may include measurementequipment measuring electricity consumption and water consumption of abuilding and transferring the measured values through a network. Asanother example, the IoT apparatuses for figuring out safety situationsmay be installed at public places or remote areas for public safety.When specific events occur, the IoT apparatuses may notify the eventsituations through a network. As another example, home appliances in ahome include a network connection function and thus a device triggeroperation of reporting a state of the home appliances or allowing a userto issue a command to the home appliances to perform a specificoperation may be performed.

The IoT device includes mobile communication modules such as long termevolution (LTE) or local area communication modules such as Bluetooth,wireless LAN (WiFi), Zigbee, and near-field communication (NFC).

The LTE terminal may also be operated on an LTE carrier frequency andmay also be operated on an ISM band.

SUMMARY

Accordingly, embodiments of the present invention are directed to theprovision of a method for dividing a kind of Clot traffics topreferentially perform a specific traffic transmission and a method fordividing CloT-dedicated network equipment and general network equipmentsupporting a CloT to allow the CloT-dedicated network equipment toprocess more CloT related signaling.

Further, embodiments of the present invention are directed to theprovision of a method for setting up a ProSe per-packet-priority value,which will be applied, in a ProSe UE-NW relay, when a packet istransferred during the provision of a relay service for MBMS trafficthrough the ProSe UE-NW relay.

Further, embodiments of the present invention are directed to theprovision of a method for modifying or generating an EPS bearer toprovide an appropriate QoS in an EPS network to remote UE receiving anEPS network service through the ProSe UE-NW relay.

Further, embodiments of the present invention are directed to theprovision of a method for allowing a remote UE accessing an IMS networkthrough a ProSe UE-network relay to acquire information on a trackingarea code (TAC) and an EUTRAN cell identifier (ECI) included in aP-Access-Network-info header field included in an SIP message andtransfer the acquired information to the IMS core network.

Objects of the present invention are not limited to the above-mentionedobjects. That is, other objects that are not mentioned may be obviouslyunderstood by those skilled in the art to which the present inventionpertains from the following description.

Various embodiments of the present invention are directed to theprovision of a communication method of a remote terminal, thecommunication method comprising: transmitting, to a relay terminal, arequest message comprising ProSe (proximity based service) per-packetpriority associated with a TMGI (temporary mobile group identity); andreceiving, from the relay terminal, a MBMS traffic transmitted based onthe ProSe per-packet priority.

The request message comprises a TMGI monitoring request message, and theTMGI monitoring request message may further comprise the TMGI and MBMSSAIs (service area identities).

The ProSe per-packet priority may be obtained from an application layerin the remote terminal.

The MBMS traffic may be received over PC5 interface.

The communication method may further comprise receiving, from the relayterminal, a TMGI monitoring response message comprising ProSe layer2group identifier.

Various embodiments of the present invention are directed to theprovision of a communication method of a relay terminal, thecommunication method comprising: receiving, from a remote terminal, arequest message comprising ProSe (proximity based service) per-packetpriority associated with a TMGI (temporary mobile group identity); andtransmitting, to the remote terminal, a MBMS traffic based on the ProSeper-packet priority.

The request message comprises a TMGI monitoring request message, and theTMGI monitoring request message may further comprise the TMGI and MBMSSAIs (service area identities).

The ProSe per-packet priority may be obtained from an application layerin the remote terminal.

The MBMS traffic may be transmitted over PC5 interface.

The communication method may further comprise: transmitting, to theremote terminal, a TMGI monitoring response message comprising ProSelayer2 group identifier.

Various embodiments of the present invention are directed to theprovision of a remote terminal comprising: a transceiver for receivingand transmitting a signal; and a controller for transmitting, to a relayterminal, a request message comprising ProSe (proximity based service)per-packet priority associated with a TMGI (temporary mobile groupidentity), and for receiving, from the relay terminal, a MBMS traffictransmitted based on the ProSe per-packet priority.

Various embodiments of the present invention are directed to theprovision of a relay terminal comprising: a transceiver for receivingand transmitting a signal; and a controller for receiving, from a remoteterminal, a request message comprising ProSe (proximity based service)per-packet priority associated with a TMGI (temporary mobile groupidentity), and transmitting, to the remote terminal, a MBMS trafficbased on the ProSe per-packet priority.

According to the embodiment of the present invention, the method fordividing a kind of Clot traffics to preferentially perform a specifictraffic transmission and the method for dividing CloT-dedicated networkequipment and general network equipment supporting a CloT to allow theCloT-dedicated network equipment to process more CloT related signalingmay be provided.

Further, according to the embodiment of the present invention, themethod for setting up a ProSe per-packet-priority value, which will beapplied, in a ProSe UE-NW relay, when a packet is transmitted during theprovision of a relay service for MBMS traffic through the ProSe UE-NWrelay may be provided.

Further, according to the embodiment of the present invention, themethod for modifying or generating an EPS bearer to provide anappropriate QoS in an EPS network to remote UE receiving an EPS networkservice through the ProSe UE-NW relay may be provided.

Further, according to the embodiment of the present invention, themethod for allowing a remote UE accessing an IMS network through a ProSeUE-network relay to acquire information on a tracking area code (TAC)and an EUTRAN cell identifier (ECI) included in a P-Access-Network-infoheader field included in an SIP message and transfer the acquiredinformation to the IMS core network may be provided.

The effects that may be achieved by the embodiments of the presentinvention are not limited to the above-mentioned objects. That is, othereffects that are not mentioned may be obviously understood by thoseskilled in the art to which the present invention pertains from thefollowing description.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 is a diagram illustrating an example of a process of registeringa terminal in a mobile carrier network and an application server,according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an embodiment of an Rx interfaceaccording to an embodiment of the present invention.

FIG. 3 is a diagram illustrating an example of a method for transferringbroadcasting related signaling according to an embodiment of the presentinvention.

FIG. 4 is a diagram illustrating an SI setup process between a basestation and an MME according to an embodiment of the present invention.

FIG. 5 is a diagram illustrating an eNB configuration update processbetween the base station and the MME according to an embodiment of thepresent invention.

FIG. 6 is a diagram illustrating an M3 setup process between an MCE andthe MME according to an embodiment of the present invention.

FIG. 7 is a diagram illustrating an MCE configuration update processbetween the MCE and the MME according to an embodiment of the presentinvention.

FIG. 8 is a diagram illustrating an example of a network structuresupporting a CIoT service according to an embodiment of the presentinvention.

FIG. 9 is a diagram illustrating another example of the networkstructure supporting a CIoT service according to an embodiment of thepresent invention.

FIG. 10 is a diagram illustrating a procedure of allowing a CloT CN nodeto acquire subscription information including a type dividing datatraffic according to purpose or characteristics of the CloT terminalfrom HSS when a CloT terminal performs an attach/tracking areaupdate/service request, according to an embodiment of the presentinvention.

FIG. 11 is a diagram illustrating a procedure of allowing a CIoTterminal to transmit a type according to a traffic model or thepurpose/characteristics of the CloT terminal when the CloT terminalperforms the attach/tracking area update/service request, according toan embodiment of the present invention.

FIGS. 12 to 14 are diagrams illustrating a method and a procedure ofapplying priority when the CIoT terminal and a CIoT network performpaging and when the CIoT terminal and the CIoT network transfers apacket, according to an embodiment of the present invention.

FIG. 15 is a diagram illustrating an example of a ProSe networkstructure.

FIG. 16 is a flow chart illustrating a procedure of receiving a ProSePer-Packet-Priority value according to an embodiment of the presentinvention.

FIG. 17 is a flow chart illustrating a procedure of receiving PPPinformation through a remote terminal.

FIG. 18 is a diagram illustrating an example of a ProSe networkstructure and an EPS and IMS network structure.

FIG. 19 is a flow chart of allocating an appropriate QoS to an EPSbearer for a relay through a PCRF.

FIG. 20 is a diagram illustrating a procedure of allowing a remoteterminal to request an appropriate QoS to an EPS bearer for a relay andallocating the QoS to the remote terminal.

FIG. 21 is a flow chart of providing a dummy value for TAC and ECI to anSIP header.

FIG. 22 is another flow chart of providing the dummy value for the TACand the ECI to the SIP header.

FIG. 23 is a flow chart illustrating an example of a procedure ofallowing a remote UE to request a relay UE to acquire ECGI and TACvalues.

FIG. 24 is a flow chart illustrating another example of the procedure ofallowing a remote UE to request a relay UE to acquire ECGI and TACvalues.

FIG. 25 is a block configuration diagram of a terminal according to anembodiment of the present invention.

FIG. 26 is a block configuration diagram of network entity according toan embodiment of the present invention.

DETAILED DESCRIPTION

FIGS. 1 through 26, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged telecommunication technologies.

In describing embodiments of the present invention, a description oftechnical contents which are well known to the art to which theembodiments of the present specification belong and are not directlyconnected with the embodiments of the present invention will not bedescribed. This is to more clearly transfer a gist of the embodiments ofthe present specification by omitting an unnecessary description.

It is to be understood that when one component is referred to as being“connected to” or “coupled to” another component in the presentspecification, it may mean that one component is connected directly toor coupled directly to another component or electrically connected to orcoupled to another component with the other component interposedtherebetween. Further, in the present specification, “comprising” aspecific configuration will be understood that additional configurationmay also be included in the embodiments or the scope of the technicalidea of the present invention.

Furthermore, constitutional parts shown in the embodiments of thepresent invention are independently shown so as to represent differentcharacteristic functions. Thus, it does not mean that eachconstitutional part is constituted in a constitutional unit of separatedhardware or one software. That is, for convenience of description, therespective constitutional parts are included by being arranged as eachconstitutional part and at least two constitutional parts of therespective constitutional parts may form one constitutional part or oneconstitutional part is divided into a plurality of constitutional partsto perform functions. An integrated embodiments and a separatedembodiment of the respective constitutional parts are also included inthe scope of the present invention unless departing from the nature ofthe present invention.

In addition, some of constituents may not be indispensable constituentsperforming essential functions of the present invention but be selectiveconstituents improving only performance thereof. The present inventionmay be implemented including only constitutional parts essential toimplement the nature of the present invention other than constituentsused only for performance improvement and the structure including onlythe essential constituents other than selective constituents used onlyfor performance improvement is also included in the scope of the presentinvention.

Hereinafter, when it is determined that in describing the embodiments ofthe present invention, the detailed description of the known art relatedto the present invention may obscure the gist of the present invention,the detailed description thereof will be omitted. Hereinafter,embodiments of the present invention will be described in detail withreference to the accompanying drawings. Further, the followingterminologies are defined in consideration of the functions in thepresent invention and may be construed in different ways by theintention of users and operators. Therefore, the definitions thereofshould be construed based on the contents throughout the specification.

In this case, it may be understood that each block of processing flowcharts and combinations of the flow charts may be performed by computerprogram instructions. Since these computer program instructions may beinstalled in processors of a general computer, a special computer, orother programmable data processing apparatuses, these computer programinstructions executed through the process of the computer or the otherprogrammable data processing apparatuses create means performingfunctions described in block(s) of the flow chart. Since these computerprogram instructions may also be stored in a computer usable memory or acomputer readable memory or other programmable data processingapparatuses that may direct a computer or other programmable dataprocessing apparatuses in order to implement functions in a specificscheme, the computer program instructions stored in the computer usablememory or the computer readable memory may also produce manufacturingarticles including instruction means performing the functions describedin the block(s) of the flow chart. Since the computer programinstructions may also be installed in a computer or other programmabledata processing apparatuses, they perform a series of operation steps onthe computer or the other programmable data processing apparatuses tocreate processes executed by the computer, such that the computerprogram instructions executing the computer or the other programmabledata processing apparatuses may also provide steps for performing thefunctions described in the block(s) of the flow chart.

Here, the term ‘-unit’ used in the present embodiment means software orhardware components such as FPGA and ASIC and the ‘˜unit’ performs anyroles. However, the meaning of the ‘˜unit’ is not limited to software orhardware. The ‘˜unit’ may be configured to be in a storage medium thatmay be addressed and may also be configured to reproduce one or moreprocessor. Accordingly, as one example, the ‘˜unit’ includes componentssuch as software components, object oriented software components, classcomponents, and task components and includes processors, functions,attributes, procedures, subroutines, segments of program code, drivers,firmware, microcode, circuit, data, database, data structures, tables,arrays, and variables. The functions provided in the components and the‘units’ may be combined with a smaller number of components and the‘units’ or may further separated into additional components and ‘units’.In addition, the components and the ‘units’ may also be implemented toreproduce one or more CPUs within a device or a security multimediacard.

Further, the exemplary embodiments of the present invention will mainlydescribe in detail the long-term evolution (LTE) and the evolved packetcore (EPC) that are a radio access network (RAN) and a core network (CN)defined in the 3rd Generation Partnership Project (3GPP) organization.However, a main subject of the present invention can be applied to evenother communication systems having the similar technical background witha slight change without greatly deviating from the scope of the presentinvention, which may be made under the determination of a person havingordinary skill in the art to which the present invention pertains.

For example, a mission critical push to talk (MCPTT) service is mainlydescribed as an example, but the present invention may be generallyapplied to other services without a great change. All informationtransmitted through each message and step is not necessarily transferredand some of the defined information may be transferred if necessary.

First, a method and an apparatus for registering a user (for example,terminal) in a mobile carrier network and an application server will bedescribed.

In order that a user attaches a mobile communication network to use aservice, mobile communication terminals (or user equipment (UE),terminal, or the like) need to be registered in the mobile carriernetwork and the application server (AS). There is a need to authenticatewhether the user is a user having authority to use the correspondingservice during the registration. The present invention provides theauthentication process on whether the user is a user having authority touse the corresponding service. Further, a method for allowing a sessioninitiation protocol (SIP) core (enhanced proxy call session controlfunction (eP-CSCF), interrogating call session control function(I-CSCF), serving call session control information (S-CSCF)) not to knowmission critical push to talk (MCPTT) identity (or identification) (ID)of a user is provided.

For this purpose, in the present invention, two types of tokens aredefined. In this case, the two types of tokens may each be called, forexample, token A and token B. Alternatively, the two types of tokens mayalso be called a first token and a second token or a first type tokenand a second type token, or the like, but are not limited thereto.Therefore, any term that may differentiate the two types of tokens maybe used. Hereinafter, for convenience of description, the token A andthe token B are used to differentiate the two types of tokens. The tokenA and the token B may be managed by an identity (ID) management server130. Further, when the ID management server 130 receives a request froma terminal 110, the ID management server 130 may provide a token to theterminal 110. According to the embodiment of the present invention, theterminal 110 may also acquire a token from several ID management servers130.

In this case, the token A may be a token used at a MCPTT service level.If the terminal 110 transmits a service request including the token A,an MCPTT server (or MCPTT application server) 160 may derive an MCPTTuser ID from the corresponding token A. By the process, an MCPTT serviceprovider may hide the MCPTT user ID from SIP cores 140 and 150.

The token B may be a token used at an SIP level. If there are no IMSidentities required to use an internet protocol multimedia subsystem(IMS IP) service, the terminal may derive and use IMS identities fromthe token B.

Hereinafter, a process of registering a terminal in a mobile carriernetwork and an application server will be described in detail by stepswith reference to the accompanying drawings.

FIG. 1 is a diagram illustrating an example of a process of registeringa terminal in a mobile carrier network and an application server,according to an embodiment of the present invention.

Referring to FIG. 1, in step 170, a user may turn on a power supply ofthe terminal 110. Accordingly, the terminal 110 may perform an attachprocedure (authentication) to a mobile communication network 120.Further, the terminal 110 may attach the mobile communication network120 to acquire an IP address, thereby acquiring IP connectivity.

In step 171, the terminal 110 enables an MCPTT client. The terminal 110attaches a uniform resource identifier (URI) of the ID management serverto start a hypertext transfer protocol over secure socket layer (HTTPS)connection. A transport layer security (TLS) connection using the HTTPSperforms unidirectional server authentication based on a servercertificate. The MCPTT client starts a user authorization procedure. TheMCPTT terminal 110 may provide user credentials information (forexample, biometrics, secureID, username/password, or the like) to the IDmanagement server 130 for verification.

In step 172, the terminal 110 may request the token A to be used for theregistration in the MCPTT server 160 to the ID management server 130. Inthis case, the terminal 110 may transfer a token request messageincluding the information requesting the token A to the ID managementserver 130. Further, in step 173, the terminal 110 may receive the tokenA from the ID management server 130 as a response thereto. In this case,the terminal 110 may receive a token response message including thetoken A from the ID management server 130.

When there is no IMS use credentials information or the correspondingcredentials information may not be used for the IMS registration, in thestep 172, the terminal 110 may additionally request the token B to theID management server 130. Therefore, in the step 173, the terminal 110may receive the token B from the ID management server 130.

In this case, according to the embodiment of the present invention, theterminal 110 may receive the token A and the token B from the same IDmanagement server 130 or different ID management servers 130.

Next, in step 174, the terminal 110 may be secure-connected with the SIPcore 140 for the authentication and registration of the SIP level. FIG.1 exemplarily illustrates that the terminal 110 is secure-connected withthe eP-CSCF 140.

Further, in steps 175 and 176, the terminal 110 may perform theregistration in the SIP cores 140 and 150 using the IMS use credentialsinformation or the token B.

When the token B is used, the eP-CSCF 140 may derive the IMS identitiesfrom the corresponding token B. At this time, the IMS identities derivedfrom the token B may be transferred to the terminal 110 while beingincluded in an OK response message. Further, the derived IMS identitiesare used in the SIP message transmitted from the terminal 110.Meanwhile, the terminal 110 may transfer the token A included in the SIPregister message to the S-CSCF 150.

Next, in step 177, the S-CSCF 150 may transfer the token A and the IMSidentities to the MCPTT server 160. The MCPTT server 160 may verify thetoken A. Further, if the token A is valid, the MCPTT server 160 mayderive the MCPTT user ID from the token A. Further, the connectioninformation between the MCPTT user ID and the IMS identities may bemanaged by the MCPTT server 160.

Next, a method for managing quality of group communication will bedescribed.

FIG. 2 is a diagram illustrating an embodiment of an Rx interfaceaccording to an embodiment of the present invention.

Referring to FIG. 2, a user terminal (or terminal, MCPTT terminal, MCPTTuser terminal) 210 may include an SIP client 213 and an HTTP client 215.Further, the SIP client 213 may be connected to an SIP core 230 throughan SIP-1 interface 270 and the HTTP client 215 may be connected to theHTTP application server (AS) 250. Further, the HTTP AS 250 may beconnected to another HTTP AS and an HTTP-2 interface 285. Further, theSIP core 230 may include an S-CSCF 231, I-CSCF 233, P-CSCF 235, and ahome subscriber server (HSS) 237. The P-CSCF 235 of the SIP core 230 maybe connected to the terminal 210 through the SIP-1 interface 270.Further, the S-CSCF 231 may be connected to the MCPTT server 240 throughan SIP-2 interface 275 and the S-CSCF 231 and the I-CSCF 233 may beconnected to an MCPTT user database through an MCPTT-9 interface. TheSIP core 230 may be connected to another core (not illustrated) throughan SIP-3 interface 277.

In this case, in the LTE mobile communication system, for QoS managementof an IMS service session provided to the user terminal 210, a first Rxinterface 260 between P-CSCF entity 235 and policy and charging rulesfunction (PCRF) entity (for example, evolved packet system (EPS)) 220may be defined and the QoS may be controlled by the correspondinginterface 260.

In the present invention, in addition to the existing LTE mobilecommunication system structure, a second RX interface 265 between anapplication server (MCPTT server, MCPTT application server) 240 and thePCRF 220 is defined. Therefore, the first Rx interface 260 between theP-CSCF 235 and the PCRF 220 and the second interface 265 between theMCPTT server 240 and the PCRF 220 may be defined. Accordingly, theapplication server 240 may provide QoS requirements to the PCRF 220without passing through the PCCF 235. For operation consistency of thePCRF 220, only one of the RX interfaces 260 and 265 for the applicationserver 240 and the P-CSCF 235 needs to be used and which of the two Rxinterfaces 260 and 265 is used may be pre-configured.

As illustrated in FIG. 2, the Rx interfaces 260 and 265 may be definedbetween the PCRF 220 and the P-CSCF 235 and/or between the PCRF 220 andthe MCPTT server 240. In this case, the PCRF 220 is hard to operatewhile receiving (transmitting) information from two entities (that is,P-CSCF 235 and MCPTT server 240). The reason is that when the MCPTTserver 240 and the P-CSCF 235 each transmit inconsistent information tothe PCRF 220, it is difficult for the PCRF 220 to process the receivedinformation. On the contrary, if the two entities 235 and 240 providethe same information, one of the two entities 235 and 240 generatesmeaningless signaling, which may not be considered as a preferredoperation. Therefore, one of the two entities 235 and 240 needs to beselected on the basis of an operator policy and/or other pre-configuredcriteria.

Both the Home and serving PLMN ID(s) are needed to identify the contactpoint for the Rx interfaces 260 and 265, in addition to existingparameters as defined in TS 23.203. The MCPTT AS 240 finds the entrypoint at the HPLMN using the home PLMN ID, the MCPTT AS 240 finds theentry point at the VPLMN using the serving PLMN ID. Within the PLMN, theinformation listed in TS 23.203 is used to find the PCRF 220.

The MCPTT AS 240 is configured with mapping information which containsan IP address range and the corresponding PLMN which is responsible forthis IP address range {(IP x . . . IP y)->PLMN ID}.

In roaming scenarios, the MCPTT AS 240 receives the UE IP address, theHPLMN ID and the VPLMN ID via MCPTT-1 signaling from the UE 210. If theconfigured PLMN entry corresponding to the UE's IP address matches theHPLMN ID sent by the UE 210, the MCPTT AS 240 selects a PCRF 220 fromthe UE's HPLMN (hPCRF) using the procedures defined in TS 23.203.Otherwise, the MCPTT AS 240 may select a PCRF 220 from either the HPLMNor the VPLMN using the procedures defined in TS 23.203. The MCPTT AS 240makes this selection based on agreements with HPLMN/VPLMN operators.

The information to be transferred through the Rx interfaces 260 and 265may be as follows.

Media or flow description (e.g. SDP);

Priority;

MCPTT Group ID;

MCPTT User ID and/or IMPU; and/or

Call type.

The MCPTT AS 240 may directly transfer all or some of the information tothe PCRF 220 through the second Rx interface 265, and the MCPTT AS 240may transfer all or some of the information to the SIP core 230 throughthe SIP-2 275 and thus the P-CSCF 235 may transfer all or some of theinformation to the PCRF 220 through the first Rx interface 260. Further,the PCRF may newly establish a bearer or modify the existing bearer,according to the collected information.

Next, a method for efficiently transferring broadcasting relatedsignaling will be described.

FIG. 3 is a diagram illustrating an example of a method for transferringbroadcasting related signaling according to an embodiment of the presentinvention.

Referring to FIG. 3, in step 370, user equipment (UE) 310 may transmitan E-UTRAN cell global identifier list to a group communication serviceapplication server (GCS AS) 360. In this case, the ECGI list may includea list of ECGIs. Further, the GCS AS 360 may define whether to transmitthe ECGI list to a broadcast multicast service center 350 according toconfiguration information. The configuration information may beavailable in the GCS AS 360 according to the operator policy and by theimplementation method. Further, according to the embodiment of thepresent invention, the configuration information may also be availablein the GCS AS 360 by the signaling between the BM-SC 350 and the GCS AS360.

In order that the GCS AS 360 activates a multimedia broadcast multicastservice (MBMS) bearer through the MB2 interface, in step 371, the GCS AS360 may transmit an activate MBMS bearer request message to the BM-SC350.

In this case, the activate MBMS bearer request message may include atleast one of temporary mobile group identity (TMGI), Flow ID, QoS, anMBMS broadcast area, and an MBMS start time. The TMGI may identify theMBMS bearer. The flow ID is included in the activate MBMS bearer requestmessage only when the TMGI is included in the activate MBMS bearerrequest message and may be used to differentiate a specific flow in MBMStraffic corresponding to the TMGI. If the flow ID is included in theactivate MBMS bearer request message, the BM-SC 350 may associate theFlow ID with the TMSI transferred from the activate MBMS bearer requestmessage and associate the Flow ID with the MBMS broadcast area. The QoSvalue may be mapped to a value representing priority of the MBMS bearer.If the MBMS broadcast area includes a list of cell IDs, the BM-SC 350maps the cell IDs to a set of MBMS service areas (SAs). According to theembodiment of the present invention, the GCS AS 360 may transmit theMBMS SA when transferring the ECGI list to the BM-SC 350. The BM-SC 350may disregard the MBMS SA received from the GCS SA 360 and rewrite theMBMS SA obtained as described above to the MAMS SA received from the GCSSA 360. When receiving the ECGI list, the BM-SC 350 may transmit theMBMS SA to the GCS AS 360 while putting the MBMS SA in the activate MBMSbearer response message. By using this, the GCS AS 360 may be used toconfigure the MBMS service data. When not receiving the ECGI list, theBM-SC 350 does not put the MBMS SA in the activate MBMS bearer responsemessage.

In step 372, the BM-SC 350 may map the cell ID list (that is, ECGIs ofthe ECGI list) to a service area list (SAIs) and may determine at leastone MBMS gateway (MBMS-GW(s)) 340 for a related area.

Further, in step 373, the BM-SC 350 may transmit a session start messageto the MBMS-GW(s) 340 determined in the step 372. The session startmessage may include an MBMS related parameter meeting 3GPP Release-12.Further, according to the embodiment of the present invention, thesession start message may include the cell ID list (that is, ECGI list).

In step 374, the MBMS-GW 340 may transmit the session start message toinvolved mobility management entity (MME(s)) 330. The session startmessage may include the MBMS related parameter meeting the 3GPPRelease-12. Further, according to the embodiment of the presentinvention, the session start message may include the cell ID list (thatis, ECGI list).

Further, in step 375, an MME 330 may transmit the session start messageto involved multicell multicast coordination entity (involved MCE(s))320. The session start message may include the MBMS related parametermeeting the 3GPP Release-12. Further, according to the embodiment of thepresent invention, the session start message may include the cell IDlist (that is, ECGI list).

Meanwhile, when choosing a receiving object of the session startmessage, the MME 330 may use the ECGI list and the MBMS SA received inthe step 374. The MME 330 may receive an MEC identifier to which thebase station (evolved Node B (eNB)) is connected or the MCE identifierto which a cell within the base station is connected during an S1 setupor an eNB configuration update. Alternatively, the MME 330 may receive acell or a base station list connected to an MCE 320 during an M3 setupor an MCE configuration update. By using the information, the MME 330may transfer the session start message only to the base station (notillustrated) corresponding to the received ECGI list. The MME 330 mayidentify the base station by looking a global eNB ID portion of theECGI. Therefore, the MME 330 may choose the suitable MCE 320 using theserving MCE information and ECGI information for each base stationduring the S1 setup or the eNB configuration update.

Next, in step 376, the MCE 320 may map the SAI list received from thesession start message received from the MME 330 to a multicast broadcastover a single frequency network (MBSFN) list and remove the MBSFN thatis not used in the corresponding ECGI list. The MCE 320 may allocateresources for the MBMS bearer to the allocated or selected MBSFNs.Further, the MCE 320 may store the cell ID list (that is, ECGI list) ofthe MBSFN in which the MBMS bearer is activated.

In step 377, the MCE 320 may transfer a session start response messageto the MME 330. The session start response message may include the MBMSrelated parameter meeting the 3GPP Release-12. Further, according to theembodiment of the present invention, the session start response messagemay include the cell ID list (that is, ECGI list) in which the MBMSbearer is activated.

Further, in step 378, the MME 330 may transfer the session startresponse message to the MBMS-GW 340. The session start response messagemay include the MBMS related parameter meeting the 3GPP Release-12.Further, according to the embodiment of the present invention, thesession start response message may include the cell ID list (that is,ECGI list) in which the MBMS bearer is activated by the session startresponse message.

Next, in step 379, the MBMS-GW 340 may transfer the session startresponse message to the BM-SC 350. The message may include the MBMSrelated parameter meeting the 3GPP Release-12. Further, according to theembodiment of the present invention, the session start response messagemay include the cell ID list (that is, ECGI list) in which the MBMSbearer is activated by the session start response message.

In step 380, the BM-SC 350 may transmit the activate MBMS bearerresponse message to the GCS AS 360. The activate MBMS bearer responsemessage may include at least one of TMGI, flow ID (If the flow ID isincluded in the activate MBMS bearer request message, the activate MBMSbearer response message may include the same value of the flow IDincluded in the activate MBMS bearer request message. Or the activateMBMS bearer response message may include the flow ID allocated from theBM-SC 350.), MBMS service description, an IP address and a port numberof the BM-SC 350 for a user data transmission plane, and expirationtime. The MBMS service description include MBMS bearer relatedconfiguration information, which may include at least one of information(for example, MBMS service area, radiofrequency, IP multicast address,APN, or the like) arranged in TS 26.346. When the BM-SC 350 allocatesthe TMGI, the expiration time represents expiration time of thecorresponding TMGI. If the BM-SC 350 receives the ECGI list in the step371, the BM-SC 350 may include the ECGI list in the activate MBMS bearerresponse message by the procedure.

If the BM-SC 350 transmits the activate MBMS bearer response message instep 379 prior to receiving the session start response message and theECGI list included in the session start response message received in thestep 379 is different from the ECGI list included in the activate MBMSbearer request message received in the step 371, the BM-SC 350 maytransmit the activate MBMS bearer response message including the ECGIlist received in the step 379 to the GCS-AS 360 and update thetransmitted activate MBMS bearer response message to notify the GCS-AS360 of the ECGI list in which a current MBMS bearer is activated.

FIG. 4 is a diagram illustrating an SI setup process between a basestation and an MME according to an embodiment of the present invention,FIG. 5 is a diagram illustrating an eNB configuration update processbetween the base station and the MME according to an embodiment of thepresent invention, FIG. 6 is a diagram illustrating an M3 setup processbetween the base station and the MME according to an embodiment of thepresent invention, and FIG. 7 is a diagram illustrating an MCEconfiguration update process between an MCE and the MME according to anembodiment of the present invention.

The MCE 320 information served by a base station 315 may be exchangedbetween the base station 315 and the MME 330 by using the followingprocedure and message.

Referring to FIG. 4, in step 410, the base station 315 may transmit anS1 setup request message to the MME 330 and in step 420, the basestation 315 may receive an S1 setup response message from the MME 330.

In this case, the S1 setup request message may be defined like thefollowing [Table 1] and [Table 2].

TABLE 1 IE/Group IE type Semantics Assigned Name Presence Range andreference description Criticality Criticality Message Type M 9.2.1.1 YESreject Global eNB ID M 9.2.1.37 YES reject eNB Name O PrintableStringYES ignore (SIZE(1..150, . . . )) Supported TAs 1..<maxnoofTACs>Supported GLOBAL reject TAs in the eNB. >TAC M 9.2.3.7 Broadcasted —TAC. >Broadcast 1..<maxnoofBPLMNs> Broadcasted — PLMNs PLMNs. >>PLMN M9.2.3.8 Identity Default Paging M 9.2.1.16 YES ignore DRX CSG Id List0..1 GLOBAL reject >CSG Id M 1..<maxnoofCSGIds> 9.2.1.62 Serving MCE O<maxnoofMCEs> 9.2.1.xx YES ignore

TABLE 2 Range bound Explanation maxnoofTACs Maximum no. of TACs. Valueis 256. maxnoofBPLMNs Maximum no. of Broadcasted PLMNs. Value is 6.maxnoofCSGIds Maximum no. of CSG Ids within the CSG Id List. Value is256. maxnoofMCEs Maximum no. of MCEs. Value is 256.

Further, referring to FIG. 5, in step 510, the base station 315 maytransmit the eNB configuration update message to the MME 330 and in step520, receive an eNB configuration update acknowledgement message fromthe MME 330.

In this case, the eNB configuration update message may be formed likethe following [Table 3] and [Table 4].

TABLE 3 IE/Group IE type and Semantics Assigned Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject eNB Name O PrintableString YES ignore (SIZE(1..150, . . . ))Supported TAs 0..<maxnoofTACs> Supported GLOBAL reject TAs in theeNB. >TAC M 9.2.3.7 Broadcasted — TAC. >Broadcast 1..<maxnoofBPLMNs>Broadcasted — PLMNs PLMNs. >>PLMN M 9.2.3.8 — Identity CSG Id List 0..1GLOBAL reject >CSG Id 1..<maxnoofCSGId> 9.2.1.62 — Default Paging O9.2.1.16 YES ignore DRX Serving MCE O <maxnoofMCEs> 9.2.1.xx YES ignore

TABLE 4 Range bound Explanation maxnoofTACs Maximum no. of TACs. Valueis 256. maxnoofBPLMNs Maximum no. of Broadcasted PLMNs. Value is 6.maxnoofCSGIds Maximum no. of CSG Ids within the CSG Id List. Value is256. maxnoofMCEs Maximum no. of MCEs. Value is 256.

Meanwhile, referring to FIG. 6, in step 610, the MCE 320 may transmit anM3 setup request (S1 setup request) message to the MME 330 and in step620, the MCE 320 may receive an M3 setup response (S1 setup response)message from the MME 330.

Further, referring to FIG. 7, in step 710, the MCE 320 may transmit anMCE configuration update message to the MME 330 and in step 720, the MCE320 receive an MCE configuration update acknowledge message from the MME330.

Meanwhile, the global MCE ID may be defined as the following [Table 5].The ID may be used at the time of establishing the M3 setup between theMCE 320 and the MME 330 or updating the MCE configuration.

TABLE 5 IE/Group IE type and Semantics Name Presence Range referencedescription PLMN M Identity MCE ID M OCTET STRING (SIZE(2)) MCE ID OOCTET STRING Extension of the Extension (SIZE(1)) Global MCE ID.

In this case, the M3 setup request message may be defined like thefollowing [Table 6] and [Table 7].

TABLE 6 IE/Group IE type and Semantics Assigned Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject Global MCE ID M 9.2.1.10 YES reject MCE Name O PrintableStringYES ignore (SIZE(1..150, . . . )) MBMS Service 1 YES reject AreaList >MBMS Service 1 to Supported GLOBAL reject Area List Item<maxnoofMBMSService- MBMS AreaIdentitiesPerMCE> Service Area Identitiesin the MCE >>MBMS Service M OCTET MBMS Area 1 STRING(2) Service AreaIdentities as defined in TS 23.003 [13]. eNB list or cell list 1 ton >Global eNB ID or ECGI

TABLE 7 Range bound Explanation maxnoofMBMSServiceAreaIdentitiesPerMCEMaximum no. of Service Area Identities per MCE. The value formaxnoofMBMSService- AreaIdentities is 65536.

Further, the MCE configuration update message may be formed like thefollowing [Table 8] and [Table 9].

TABLE 8 IE/Group IE type and Semantics Assigned Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject Global MCE ID O 9.2.1.10 YES reject MCE Name O PrintableStringYES ignore (SIZE(1..150, . . . )) MBMS Service 0..1 YES reject AreaList >MBMS Service 1 to Supported GLOBAL reject Area List Item<maxnoofMBMSService- MBMS AreaIdentitiesPerMCE> Service Area Identitiesin the MCE >>MBMS Service M OCTET MBMS Area 1 STRING(2) Service AreaIdentities as defined in TS 23.003 [13]. eNB list or cell list 1 ton >Global eNB ID or ECGI

TABLE 9 Range bound Explanation maxnoofMBMSServiceAreaIdentitiesPerMCEMaximum no. of Service Area Identities per MCE. The value formaxnoofMBMSService- AreaIdentities is 65536.

Next, a method for managing quality of group communication will bedescribed.

Throughout the present specification, the CloT represents an IoT service(cellular IoT) using a cellular network. The cellular network means amobile communication network and includes 2G represented by GERAN, 3Grepresented by GPRS, and 4G represented by LTE. The CloT service maymean a cellular service for supporting an internet of things (IoT)terminal and may mean a service transmitting a small capacity of datathrough the cellular network. Further, the CloT service may include amachine type communication (MTC) service.

The Clot is that a large number of terminals may be simultaneouslyconnected to the network and the network may simultaneously transferdata to a large number of terminals. Therefore, it is expected that anetwork congestion situation may be more severe than a general cellularsystem. Therefore, a method for reducing a congestion situation due toCloT by setup and signaling between network apparatuses and a method forprocessing priority depending on a kind of CloT traffic in a congestionsituation are required. The kind of CloT traffic may include a periodicreport data, a data reported when an aperiodic event is generated, acommand data issuing a command through the network to allow an apparatusto trigger a specific operation, an update data for updatingsoftware/firmware of an IoT apparatus and changing a setup thereof, adata for public safety, or the like. To increase the quality of servicein the network congestion situation, a CloT data depending on theaperiodic event needs to be preferentially transferred through thenetwork over the periodically transferred CloT data. Otherwise, a usermay late receive a CloT data depending on an aperiodic data notifyingthe occurrence of the emergency situation late due to the congestion ofthe periodically transferred CloT data, which may cause the reduction inquality of service and reliability that the user feels.

For convenience, in the present invention, a user plane data transmittedfrom a terminal is called a data and a control plane data is calledsignaling. The term is not limited the name and other terms dividing apacket transmitted for providing a data and a control signal transmittedfor providing a service in a network may be used. Further, a termindicating control information used in the following description, a termmeaning a user data transferred to an application server, a term meaningsignaling for transferring control information between networkapparatuses, a term (for example, event report data, periodic reportdata) indicating a kind of traffics, a term indicating components of anapparatus, etc., are exemplified for convenience of explanation.Accordingly, the present invention is not limited to terms to bedescribed below and other terms having the equivalent technical meaningmay be used.

Further, some of the terms and names defined in the 3rd generationpartnership project long term evolution (3GPP LTE) may be used. However,the present invention is not limited to the terms and names but may alsobe identically applied to the system according to other standards.

FIG. 8 is a diagram illustrating an example of a network structuresupporting a CIoT service according to an embodiment of the presentinvention and FIG. 9 is a diagram illustrating another example of thenetwork structure supporting a CIoT service according to an embodimentof the present invention.

The LTE terminal 817 and the IoT terminal 810 mean a mobile terminalthat may perform radio communication and may be, for example, a personaldigital assistant (PDA), a smart phone, a mobile phone, a tabletcomputer, a notebook, etc., that include a communication function andmay mean a measurement terminal for confirming water consumption,electricity consumption, and temperature, a terminal for recognizing andreporting a situation such as a fire alarming device and an earthquakealarming device, and home appliances having a communication functionsuch as an air conditioner, a refrigerator, an air cleaner, a boiler,and a cleaner, in addition to individual equipment. In addition to theabove-mentioned kinds, all things that may perform communications willbe called as the IoT terminal in the present invention. Further, theterminal using the cellular network among the IoT terminals is calledthe CloT terminal. Further, for convenience of explanation, the terms ofthe CloT terminal, the IoT terminal, the terminal, the user terminal, orthe like may be used together. The CloT terminal 810 may mean theterminal transmitting a small capacity of data in the LTE network. Theapparatus, function, and operation for a CloT service according to thepresent invention include an apparatus, a function, and an operation forsmall data transmission in the LTE network. The IoT data may mean a datawhich the IoT terminal transmits or a small capacity of data which anykind of terminals transmit.

For the CloT, the existing network equipment may be changed. Forexample, a CloT-dedicated base station may be present and a base stationin which a CloT function is added to the existing base station may bepresent. In the present invention, the CloT-dedicated base station iscalled a C-BS 820 for convenience. The base station in which the CloTfunction is added to the existing base station is called a C-eNB 825 forconvenience. The present invention is not limited to the correspondingterms and therefore other terms having the equivalent technical meaningmay be used. Similarly, a core network present in the cellular networkmay also be used only for the Clot. In the present invention, this iscalled a CloT core network (CN) node 830 and is called a C-SGN in thepresent 3GPP, but the present invention is not limited to thecorresponding term but other terms having the equivalent technicalmeaning may be used. The CloT CN node 830 may not only perform contextmanagement, mobility management, and signaling session management of theCloT terminal 810, but may also transfer the data of the terminal 810 toan application server (AS) 840 or transfer the data received from theapplication server 840 to the terminal 810. That is, the CloT CN node830 may provide functions of gateways (GWs) 865 and 867 to the CloTterminal and perform a function of an S-GW 865/P-GW 867 of receiving adata from the C-BS 820 or the C-eNB 825 and routing the received data tothe application server 840. In this case, as illustrated in FIG. 8, theCloT CN node 830 may connect the CloT terminal 810 to a signaling planeand may not connect the CloT terminal to a user plane and may transmitthe CloT data to the signaling plane or may transmit a small capacity ofdata to the signaling plane.

Further, as illustrated in FIG. 9, when the CloT CN node 830 establishesboth of the connection of the CloT terminal 810 to the signaling planeand the connection of the CloT terminal 810 to the user plane, the CloTterminal 810 establishes a bearer for the user plane with the C-BS 820or the C-eNB 825 and the C-BS 820 or the C-eNB 825 establishes thebearer for the user plane with the S-GW 865/P-GW 867. In this case, theClot terminal 810 may transmit the user plane data through the C-BS 820or the C-eNB 825 and the C-BS 820 or the C-eNB 825 routes the user planedata to the S-GW 865/P-GW 867 to support data communication.

The CloT CN node 830 performs a similar role to the MME 860 of theexisting LTE network. According to the embodiment, the CloT CN node 830may be an apparatus in which the CloT function is added to the MME 860providing the equivalent technology. The CloT CN node 830 may beconnected to several C-BSs 820 and several C-eNBs 825. It is obviousthat in the 3GPP, this is called an S1 connection and may be anotherterm meaning an interface between the C-BS 820 or the C-eNB 825 and theCloT CN node 830. The C-eNB 825 is a base station that supports the CloTservice but also supports a general LTE service. Therefore, the CloTterminal 810 and the general LTE terminal 817 may also be connected tothe C-eNB 825 to use a communication service. On the other hand, theC-BS 820 is a base station supporting only the CloT service andtherefore the general LTE terminal 817 is not connected and only theCloT terminal 810 is connected to the C-BS 820 to use a communicationservice. The CloT CN node 830 does not find whether the base stations820 and 825 is the dedicated base station 820 for CloT or the generalbase station, recognizes that the S1 connection is established totransmit signaling or data. The CloT CN node 830 first transfers pagingsignaling to the C-BS 820 or the C-eNB 825 most recently connected tothe terminals 810, 815, and 817 to transmit data or signaling. If thefirst paging signaling fails, the CloT CN node 830 transmits the pagingsignaling to all the base stations 820 and 825 in the area in which theterminals 810, 815, and 817 are present to transmit paging to theterminals 810, 815, and 817. In this case, the C-eNB 825 that isproviding the general LTE service together receives the paging signalingnotwithstanding that the paging signaling is not for the terminals 815and 817 served by the C-eNB itself. In this case, the unnecessary pagingsignaling may cause the congestion in the C-eNB 825 providing thegeneral LTE service to reduce the quality of service of the general LTEservice user. Therefore, after the first paging signal fails, the CloTCN node 830 may first transmit the paging signaling to the C-BS 820 toprevent the congestion from occurring in the C-eNB 825 providing thegeneral LTE service. For the operation as described above, when the CloTCN node 830 is SI-connected to the C-BS 820 or the C-eNB 820, the basestation may differentiate and notify its own capability, such that it ispossible to differentiate whether the base station to which the CloT CNnode 830 is S1-connected is the dedicated base station for CloT (C-BS)820 or the CloT support base station (C-eNB) 825 that also provides thegeneral service.

Hereinafter, a method for dividing a kind of Clot traffics topreferentially perform a specific traffic transmission and a method fordividing network equipment for CloT and general network equipmentsupporting a CloT to allow the network equipment for CloT to processmore CloT related signaling will be described.

The embodiment of the present invention mainly describes the LTE systemdefined in the 3GPP but may be similarly applied in radio communicationssuch as WLAN and Bluetooth. According to the present invention, a methodand an apparatus for exchanging relay related information between a corenetwork and a base station to support an UE to network relay functionthat is one of proximity based service (ProSe) functions for publicsafety and a method and an apparatus for controlling a terminal to allowa base station to support a relay function will be described.

The CloT traffic may have a low data rate, small capacity, delaytolerant, periodicity/aperiodicity (event), responserequired/non-required characteristics. In more detail, the data trafficperforming event reports such as smoke alarm, fault alarm, powershortage alarm, and temperature alarm may transmit a small capacity ofdata only to an uplink, may not require a response, and does not occurall the time, but may occur only when an event is generated. The trafficmay be used in the IoT service associated with public safety andtherefore may have higher priority than other data traffic. Further, thedata traffic performing a periodic report such as measurement of gasconsumption, measurement of water consumption, and measurement ofelectricity consumption may transmit a small capacity of data to anuplink, receive a response to a result of the measurement report, andmay be periodically generated all the time in aminute/hour/day/month/year unit. The data traffic that turns on/off apower supply of the terminal or triggers the specific operation maytransmit a small capacity of data to an uplink, receive a response tooperation performance through a downlink, and may be generatedperiodically or aperiodically. The data needs to be performed byallowing the CloT terminal to issue a command or receive the command andtherefore if the data is not transferred within a predetermined time, itis much time to trigger the device to reduce the IoT service quality,such that the data traffic needs to be preferentially process over otherdata traffic in the network. The data traffic for updatingsoftware/firmware, updating a set value, etc. of the IoT terminal mayuse the relatively large capacity as the uplink and the downlink and isthe data traffic that relatively intermittently occurs. The data trafficmay be used to update the security related information, update the setupfor the IoT equipment added within the IoT approach network, etc.

The embodiment of the present invention proposes data trafficcategorization. In this case, the CloT terminal and the network mayapply other priorities depending on the data traffic category to processthe IoT data. The data traffic category may be divided according to theabove-mentioned data characteristics. The following Table 10 is anexample showing the category depending on data traffic attributes.

TABLE 10 Traffic property Category Data Size Capacity that may be put inone packet, Capacity requiring at least one packet, Large capacityPeriodic property Periodic (30 minutes, 1 hour, 1 day, 1 week, 1 month,1 year, or the like) Event oriented (upon occurrence of specificsituation) Response required Response required data Responsenon-required data Public Public Safety safety/Emergency Emergency

The category of the above Table 10 divides data based oncapacity/periodicity/response necessity/public safety/emergency and maynot necessarily depend on the division as described above and mean allthe categories that may be divided depending on at least one trafficattribute of capacity/periodicity/response necessity/publicsafety/emergency.

It may be expected that the IoT data generally has small capacity, butall the IoT data may not be transmitted by one packet and a large amountof data may be transmitted and received in the case of updating thesetup of the equipment or updating the software. Therefore, it may bedivided whether the IoT data may be included in one packet or severalpackets, or whether a large capacity of data is required. In the presentinvention, any division depending on the data capacity is also included.

The IoT data may be a data that is transmitted and received to and fromsmall equipment such as a sensor or measurement equipment and theequipment may transmit a data when the measured value is periodicallyreported or the specific situation occurs. For example, the IoT terminalmeasuring water consumption and electricity consumption may transmit themeasurement report in a period of 1 day, 1 week, or 1 month. When theIoT terminal that may transmit a fire alarm and an earthquake alarmsenses smoke or is equal to or higher than a specific temperature orsenses a strong shock, the IoT terminal may report the relevant data andthus generate a data when the specific situation occurs withoutperiodicity. Therefore, the data traffic that the IoT terminal reportsmay have periodicity or may be generated as event-oriented data trafficand may be sub-divided in a unit of minute, hour, day, month, year,etc., when having periodicity.

The Iot terminal may transmit a data not requiring a response to thetransmitted data. For example, when the measured value is reported, onlythe measured value is transmitted and the response thereto may not berequired. Alternatively, the IoT terminal may transmit the datarequiring the response to the data. For example, when a currenttemperature inside a house is queried to an air conditioner supportingthe IoT service, the air conditioner receiving the query needs torespond to the current temperature. Alternatively, when the airconditioner is queried to be operated, the air conditioner may transmitthe response that a command is processed well to notify a user that acommand is performed well. Therefore, the data that the IoT terminaltransmits may be divided depending on whether the response is requiredor not.

The IoT terminal may be used for a commercial purpose such as a smarthome and a smart grid and a public safety/emergency purpose forperceiving a natural disaster or an accident. For example, when a fireor an earthquake occurs in sparsely settled regions, a small IoTterminal installed therearound may sense a situation to transmit areport. When the situation in which the public safety is threatenedoccurs, the processing thereon needs to be more quickly performed thanother data. Therefore, if the IoT terminal transmits the data trafficfor the public safety or the emergency, the IoT terminal may designatethe traffic category so that the data traffic is preferentiallyprocessed over the general commercial data traffic. The presentinvention includes dividing the characteristics of the IoT terminal byusing at least one of the listed attributes(capacity/periodicity/response necessity/public safety/emergency).Further, the present invention includes processing meeting thecharacteristics in the network based on the divided characteristics.

Meanwhile, the traffic characteristics may e interpreted as the priorityof the IoT data that the IoT terminal transmits. That is, the data forthe emergency or the public data needs to be preferentially processedover the general measurement report data. Therefore, the trafficcharacteristics may be substituted into the priority of the data andthen applied. For example, the QCI value may be allocated to each kindof data by using a QoS class identifier (QCI) that is an indexrepresenting the QoS, thereby applying the priority. As a more detailedexample, QCI=6 may be allocated to the data for the public safety andQCI=9 may be allocated to the general measurement report data. Theterminal may transmit data including the QCI value and the base station,the MME, or the SGSN perceiving the data preferentially processes datafor QCI=6 over data for QCI=9, thereby applying the priority.

FIG. 10 is a diagram illustrating a procedure of allowing a CloT CN nodeto acquire subscription information including a type dividing datatraffic according to purpose or characteristics of the CloT terminalfrom HSS when a CloT terminal performs an attach/tracking areaupdate/service request, according to an embodiment of the presentinvention.

According to the embodiment illustrated in FIG. 10, the data trafficcategory may be used in the network while being stored as subscriptioninformation of a CloT terminal 810.

In step 1010, an RRC connection between the CloT terminal 810 and theC-BS 820 may be established.

Further, in step 1020, the CloT terminal 810 may transmit an attachrequest to be connected to the CloT CN node 820. Alternatively, theposition of the CloT terminal 810 is changed and thus the CloT terminal810 may transmit a tracking area update to the CloT CN node 820.Alternatively, the CloT terminal 810 may transmit a service request totransmit data to the CloT CN node 820.

Further, in step 1030, the CloT CN node 820 may perform anauthentication procedure on the HSS 350. In this case, the CloT CN node820 may receive the subscription information including the divisionaccording to the data traffic characteristics used by the CloT terminal810 from the HSS 850. Further, the CloT CN node 820 may store, as aterminal context in step 1040, the subscription information includingthe division according to the data traffic characteristics received inthe step 1030 and used by the CloT terminal 810. Further, in step 1050,the CloT CN node 820 and the CloT terminal 810 may perform the remainingprocedure.

The division according to the data traffic characteristics used by theCloT terminal 810 may be the terminal context divided into the datatraffic divided according to the purpose or characteristics of theterminal and may be a terminal context divided according to the datatraffic characteristics mainly used by the terminal 810. The terminalcontext may be present as an identifier like a type, the type mayrepresent the type of the data traffic or the type of the CloT terminal,and the type of the CloT terminal may mean the data trafficcharacteristics. Alternatively, a priority value that the terminal 810may use may be represented. For example, the terminal context mayinclude a list of QCI values. The terminal 810 for the public safetyuses a value corresponding to the highest priority, and therefore maytransfer the terminal context including the value corresponding to thehighest priority or the QCI value. Further, the terminal 810 performingthe measurement function may be subscribed to use a value correspondingto low priority. In this case, the CloT CN node 830 may include thepriority value or the QCI value corresponding thereto. The terminal 810that may transmit various kinds of traffics needs to be able todifferentiate priority for each message, and therefore the CloT CN node830 may include the priority values or the QCI values that may be usedby the corresponding terminal 810.

The CloT CN node 830 may provide different service levels for eachterminal context based on the terminal context. For example, the publicsafety IoT terminal 810 may be authenticated by acknowledging that theterminal 810 is for the public safety when being connected to thenetwork and may process the traffic of the corresponding terminal81—after performing the procedure based on the priority. As anotherexample, the terminal 810 for measuring gas consumption may include theinformation on the data traffic characteristics periodically reportingthe measured value to the subscription information when it is connectedto the network and always allocate priority corresponding to theperiodic report data traffic to the terminal 810 for measuring gasconsumption based on the information. As another example, the user mayuse the CloT support home appliances configuring the smart home usingthe IoT, in more detail, an air conditioner supporting the CloT functionfor the device trigger, and therefore the event-oriented data trafficcharacteristics may be found. Further, since the immediate triggeringdetermines the quality of service, the air conditioner needs to beprocessed with higher priority than the terminal having the periodicdata characteristics, such that the air conditioner may be processedwith the corresponding priority, including the subscription informationhaving the information on the event-oriented data trafficcharacteristics. The priority processing proposed in the presentinvention may be priority considered together with the normal LTEtraffic and may be priority considered between the CloT traffics.

Further, the priority value or the list of the priority values stored interminal context for the terminal 810 to use in the IoT data may betransferred to the terminal 810 through a non-access stratum (NAS)procedure (for example, attach, TAU, service request) of the terminal810.

FIG. 11 is a diagram illustrating a procedure of allocating a CIoTterminal to transmit a type according to a traffic model or thepurpose/characteristics of the CloT terminal when the CloT terminalperforms the attach/tracking area update/service request, according toan embodiment of the present invention.

FIG. 11 illustrates an example in which the embodiment described withreference to FIG. 10 is added. That is, in step 1110, an RRC connectionbetween the CloT terminal 810 and the C-BS 820 may be established.Further, when the CloT terminal 810 transmits the attach request, thetracking area update, the service request message to the CloT CN node830 in step 1120, the message may include an identifier meaning thedivision according to the data traffic characteristics used by the CloTterminal 810, an identifier divided by the data traffic dividedaccording to the purpose/characteristics of the terminal, or anidentifier divided according to the data traffic characteristics mainlyused by the terminal. In this case, the CloT CN node 830 may look at theidentifier transmitted by the terminal to divide the data trafficcharacteristics used by the terminal.

The CloT CN node 830 may authenticate the information on the identifierof the terminal 810 based on the procedure of authenticating the HSS 850in step 1130 and may omit the procedure of authenticating theinformation on the identifier of the terminal 810 according to theembodiment of the present invention.

Next, the CloT CN node 830 may store the terminal context including theidentifier that may divide the traffic characteristics in step 1140 andperform the remaining procedures in step 1150. Next, the terminal 810may look at the identifier (identifier that may divide the data trafficcharacteristics) stored in the terminal context to provide a servicemeeting the characteristics.

FIGS. 12 to 14 are diagrams a method and a procedure of applyingpriority when the CIoT terminal and a CIoT network perform paging andwhen the CIoT terminal and the CIoT network transfers a packet,according to an embodiment of the present invention.

The method for defining priority may follow an operator's policyoperating a cellular network. For example, priority may be allocated totraffic having the event report characteristics, allocated to traffichaving the public safety or emergency characteristics, or allocated tothe traffic for the device trigger. Alternatively, the lowest prioritymay be allocated to the IoT terminal 810 having a traffic modeltransmitting the periodic data.

According to one described with reference to FIGS. 10 and 11, the methodfor applying priority illustrated in FIGS. 12 to 14 may be appliedbetween the CloT terminal 810 and the CloT networks, 820, 825, 830, 840,and 850 after the CloT CN node 830 performs the procedure of storing aterminal context.

Referring to FIG. 12, the CloT CN node 830 determines the pagingpriority based on the identifier considering the data traffic attributestored in the terminal context to transfer a paging signal processedbased on priority to the C-BS 820.

Describing in more detail, when the traffic for the terminal 810 isgenerated from the application server 840 to transmit paging 1210 forthe terminal 810, the CloT CN node 830 may look at the terminal contextto determine the identifier for the data traffic characteristics and thepriority. Further, the CloT CN node 830 may determine the pagingpriority based on the identifier and transmit a paging signal 1220,which is processed with priority, to the C-BS 820 or the C-eNB 825. TheC-BS 820 or the C-eNB 825 may process the paging signal in the orderthat the paging is requested to transmit the paging signal 1220, whichis processed with priority, to the CloT terminal 810.

Referring to FIG. 13, the CloT CN node 830 may transfer a paging message1310 to the C-BS 820, including the identifier representing the priorityin the paging request and allow the C-BS 820 to page the terminaldepending on the priority included in the paging request.

Describing in more detail, the CloT CN node 830 may include anindication representing a priority level in the paging request message1310 transmitted to the C-BS 820 or the C-eNB 825. The C-BS 820 or theC-eNB 825 receiving the paging request message 1310 may look at theindication representing the priority level to determine the priorityamong different paging requests 1320. Further, when the priority of thereceived paging request message 1310 is ahead of different pagingrequests 1320, the paging may be first performed on the received pagingrequest message 1310. According to the embodiment of the presentinvention, the indication representing the priority level may berepresented by being divided the priority level into various levelsand/or may represent only the highest priority and/or only the lowestpriority.

Referring to FIG. 14, when an uplink/downlink data is transmittedbetween the CloT terminal 810 and the CloT networks 820, 825, 830, 840,and 850, the priority may be applied depending on the trafficcharacteristics.

Describing in more detail, the CloT CN node 830 or the C-BS 820/C-eNB825 may transfer a packet by applying priority to an uplink/downlinkpacket based on the terminal context considering the data trafficcharacteristics. Further, the CloT terminals 810 and 815 may perform anuplink transmission of an indication representing the data trafficcharacteristics and the priority by including the indication in a packetheader. The present example illustrates that the CloT CN node 830includes the P-GW function. However, when the P-GW is present by beingseparated from the CloT CN node 830 to establish the user plane bearer,the P-GW and the S-GW may be connected to the C-BS 820 or the C-eNB 825to transmit the packet to the user plane.

According to the present embodiment, in the case of the downlink, theCloT CN node 830 may receive a packet 1410 from the application server840. The CloT CN node 830 may acknowledge to which one of CloT UEs 810and 815 the packet 1410 is transferred by looking at a destination IPaddress of a packet. Further, the CloT CN node 830 may acknowledge theterminal context matching the IP. If the identifier for the data trafficcharacteristics is present in the terminal context, the prioritydepending on the corresponding traffic characteristics may be applied.Therefore, when packets 1420 and 1425 are transferred to the C-BS 820 orthe C-eNB 825, the priority depending on the data trafficcharacteristics may be applied to preferentially transfer a packet for aspecific user or determine the packet for the specific user as thelowest priority and transmit it. Further, the C-BS 820 or the C-eNB 825may transmit the received packet to the terminals 810 and 815 dependingon the priority.

In the case of the uplink, the CloT terminals 810 and 815 may transmittransmission packets 1430 and 1435 to the CloT CN node 830 as an NASmessage. Alternatively, the CloT terminals 810 and 815 may transfer thepackets 1430 and 1435 to the base station (C-BS 820 or C-eNB 825) as theRRC message and the base station (C-BS 820 or C-eNB 825) may alsotransfer the packets 1430 and 1435 to the CloT CN node 830 through an S1message. Alternatively, when the user plane is established, the CloTterminals 810 and 815 may also transfer the packets 1430 and 1435through the user plane bearer. The NAS message means a message that istransparent to the base station (C-BS 820 or C-eNB 825) and transmittedand received between the terminals 810 and 815 and the CloT CN node 830.The S1 message means a message transmitted and received between the basestation (C-BS 820 or C-eNB 825) and the Clot CN node 830.

In the three methods according to the detailed embodiment of the presentinvention, a method for transferring, by CloT terminals 810 and 815, anuplink packet is proposed. First, when transmitting the IoT packet asthe NAS message, the CloT terminals 810 and 815 may represent the datatraffic characteristics in a differentiated service code point (DSCP) ofa header of the NAS message or the IP packet included in the NAS messageAs a more detailed example of the DSCP, in the case of the data traffictransmitting the measurement report, a DSCP value having the delaytolerant and the low priority may be set. The indication of the trafficcharacteristics included in the header of the NAS message may be appliedto the priority processing by allowing the CloT CN node 830 to receiveand confirm the message. In this case, the CloT CN node 83 may comparethe indication of the traffic characteristics included in the header ofthe NAS message with the stored terminal context to determine whether toapply the priority meeting the corresponding traffic characteristics.Alternatively, the priority may be applied as the indication of themessage transmitted by the terminals 810 and 815. When the terminals 810and 815 mark the IP packet to the DSCP and transmits the marked IPpacket, the CloT CN node 830 may perform the P-GW role to open the IPpacket and confirm the DSCP marking and transmit it to the applicationserver by applying the priority based thereon. Alternatively, theterminals 810 and 815 may transfer the NAS message including thepriority value of the IoT packet to the CloT CN node 830. The NASmessage transmitted from the terminals 810 and 815 includes a beareridentifier and the IoT data and may further include the priority valueor the QCI value of the IoT packet. In the above description, the headerof the NAS message means this. The clot CN node 830 looks at the NASmessage transmitted from the terminals 810 and 815 to check the priorityfor the corresponding traffic, thereby performing the priorityprocessing.

Second, the terminals 810 and 815 may transmit the corresponding RRCmessage to the base station (C-BS 820 or C-eNB 825), including theindication meaning the data traffic characteristics in the RRC messagealong with the packet 1435. The indication meaning the trafficcharacteristics may be a value representing the priority of the trafficor the QCI value. The base stations 820 and 825 may identify theindication meaning the data traffic characteristics included in the RRCmessage and applies the corresponding priority to transmit it to theCloT CN node 830. The base station (C-BS 820 or C-eNB 825) configuresthe packet received from the terminal as the S1 message and transmitsthe packet to the CloT CN node. In this case, the base station maytransfer the S1 message that includes an indication corresponding to theindication meaning the data traffic characteristics received from theterminals 810 and 815. The CloT CN node receiving the S1 message mayapply the priority by looking at the indication included in the S1message to transmit the packet to the application server 840 or theP-GW. The indication meaning the traffic characteristics may mean thevalue representing the priority of the traffic to be transmitted fromthe terminals 810 and 815 or the QCI value.

Next, a method for allocating priority to multimedia broadcast multicastservice (MBMS) traffic in a proximity based service (ProSe) userequipment-network (UE-network) relay will be described.

According to one embodiment of the present invention, in a process ofproviding a relay service for MBMS traffic through the ProSe UE-network(NW) relay, a ProSe per-packet-priority (PPP) value to be applied when apacket is transmitted may be set in the ProSe UE-NW relay.

FIG. 15 is a diagram illustrating an example of a ProSe networkstructure.

Referring to FIG. 15, by the proximity service between the terminal, aservice may be received through a network using a ProSe UE-NW relay1520.

The UE-NW rely UE (or relay UE) 1520 serves as a relay that transfers aservice provided from a cellular network 1590 to the remote UE 1510,while being within the coverage of the base station (eNB) 1530Meanwhile, the cellular network 1590 may include a base station 1530, aProSe ProSe function 1540, an MME 1550, a gateway (GW) 1560, an HSS1570, a BMSC 1575, or the like.

Meanwhile, the UE-NW relay UE 1520 may receive various kinds ofinformation for registering that the UE-NW relay UE 1520 is a relay andproviding a relay service through the EPS network 1590 or may prepare arelay service such as a generation of a PDN connection for providing anIP service to the remote UE 1510. Further, when the relay service isprepared, the UE-NW relay UE 1520 broadcasts an announcement message fordirectly notifying that the UE-NW relay UE 1520 is a relay according toa discovery method, such that the remote UE 1510 may discover the UE-NWrelay UE 1520. Alternatively, the UE-NW relay UE 1520 receives adiscovery solicitation message transmitted when a remote UE 1510therearound finds out a relay, and if meeting the correspondingcondition, the UE-NW relay UE 1520 transmits a discovery responsemessage and thus the remote UE 1510 may also discover the UE-NW relay UE1520. The remote UE 1510 may select the wanted relay among thediscovered UE-NW relay UEs 1520 to setup the connection between thecorresponding UE-NW relay UE 1520 and the remote UE 1510, such that theremote UE 1510 may receive a service through the cellular network 1590.

In this case, the ProSe per-packet-priority value to be applied when theMBMS traffic is transmitted may be setup in the ProSe UE-NW relay UE1520.

FIG. 16 is a flow chart illustrating a procedure of receiving a ProSePer-Packet-Priority value according to an embodiment of the presentinvention.

Referring to FIG. 16, according to the embodiment of the presentinvention, the relay UE 1520 may be allocated with a default PPP valuein a provisioning step.

The ProSe UE-NW relay UE 1520 may perform a procedure of preparing arelay service through a service authorization process. In step 1610, theProSe remote UE 1510 may transmit a service authorization requestmessage to the ProSe function 1540 for the service authorizationprocess. Further, in step 1630, the ProSe function 1540 may transmit theservice authorization response message to the remote UE 1510. Accordingto the embodiment of the present invention, the ProSe function 1540 mayreceive the information on the ProSe service for the remote UE 1510 fromthe Hss 1570 an SH request message and an SH response message of thesteps 1620 and 1630, if necessary.

Meanwhile, the UE-NW relay 1520 that may provide the relay service orprovides the relay service may provide the relay service or may alsotransmit the relay indication for indicating the terminal providing therelay service when the service authorization request message istransmitted to the ProSe function 1540 in step 1640. In this case, theProSe function 1540 may confirm whether the terminal 1520 transmittingthe service authorization request message in the step 1640 is a terminalproviding the relay service based on its own information. Alternatively,the ProSe function 1540 may transmit a message (for example, SH request)querying whether the terminal 1520 transmitting the serviceauthorization request message in the step 1640 to the HSS 1570 is aterminal providing the relay service in step 1650 and receive andconfirm the response message (for example, SH response) thereto from theHSS 1570 in step 1655. In this case, in the step 1655, the HSS 1570 maytransmit the SH response message including the relay indication.

Further, the ProSe function 1540 may transfer the default PPP value tobe used when the UE-NW relay UE 1520 provides the relay service for theMBMS traffic to the relay UE 1520 through the service authorizationresponse message in step 1660, depending on the value stored in theProSe function 1540 or the value included in the message received fromthe HSS 240 in the step 1655. According to the embodiment of the presentinvention, the default PPP value may be allocated to the relay UE 1520through a 3rd party application server, in addition to the ProSefunction 1540 or the HSS 1570.

Meanwhile, in step 1670, the remote UE 1510 notifies the relay UE 1520of the wanted TMGI information when receiving the MBMS traffic torequest monitoring the MBMS traffic for the corresponding TMGI. Further,the requested relay UE 1520 transfers ProSe L2 group ID_trafficindicating a ProSe group to be used to transmit the MBMS trafficcorresponding to the TMGI to the remote UE 1510 as a response to therequest. Further, in step 1680, the relay UE 1520 may receive the MBMStraffic for the TMGI. In this case, the relay UE 1520 broadcasts thecorresponding MBMS traffic to the ProSe L2 group ID_traffic through aPC5 interface depending on the default PPP value allocated from theProSe function 1540 in step 1690.

According to another embodiment of the present invention, whenbroadcasting the MBMS traffic to the ProSe L2 group ID_traffic, therelay UE 1520 refers to the default PPP value and the number of remoteUEs 1510 requesting the TMGI monitoring to the relay UE to define theper-packet-priority (PPP) value, thereby transmitting the traffic. Forexample, when the default PPP value is 3 and the terminal requesting theTMGI monitoring is one, the PPP value is set to be 3, while when theterminal requesting the TMGI monitoring is equal to or more than 5, ahigher PPP value may be set to be 2 to transmit traffic.

FIG. 17 is a flow chart illustrating a procedure of receiving PPPinformation through a remote terminal.

Referring to FIG. 17, according to the embodiment of the presentinvention, the relay UE 1520 may receive the ProSe per packet priority(PPP) information through the remote UE 1510.

The remote UE 1510 accesses the UE-NW relay UE 1520 and then in step1710, may request the TMGI monitoring to transmit the TMGI monitoringrequest message for requesting the MBMS traffic transmissioncorresponding to a specific TMGI to the relay UE 1520. In this case, theTMGI monitoring request message transfers the TMGI and MBMS service areaidentities (SAIs) and the per packet priority (PPP) related informationon the MBMS traffic acquired from an application layer of the remote UE1510 itself to the relay UE 1520. That is, the remote UE 1510 maytransmit information on priority that the remote UE 1510 wants toreceive to the relay UE 1520.

Describing in more detail, the application layer of the remote UE 1510may determine the ProSe PPP related information. In this case, theapplication layer of the remote UE 1510 may determine the PPP relatedinformation associated with the specific TMGI that the remote UE 1510requests. Further, the application layer that is an upper layer of theremote UE 1510 may transmit the determined PPP related information tothe ProSe layer. Accordingly, the ProSe layer of the remote UE 1510 maytransmit the PPP value, which is received from the application layer andincluded in the TMGI monitoring request message, to the relay UE 1520.

As the PPP related information, the PPP value allocated from theapplication layer of the remote UE 1510, a call type (for example,information, or the like of emergency/imminent peril/normal) for thecorresponding service, or the like may be used.

The relay UE 1520 determines the PPP value to be actually used based onthe information. When the relay UE 1520 has the existing PPP value forthe corresponding TMGI, the relay UE 1520 disregards the existing PPPvalue and may substitute the existing PPP value into a new PPP value.Alternatively, the case in which the relay UE 1520 discards the new PPPvalue and continuously uses the existing PPP value may be possible.

Further, in step 1720, the relay UE 1520 may transmit the TMGImonitoring response message to the remote UE 1510. In this case, therelay UE 1520 may also transmit the L2 Group ID_traffice that is theallocated ProSe group information and according to the embodiment of thepresent invention, may also transmit the PPP value to be used to theremote UE 1510 by including the PPP value in the TMGI monitoringresponse message. According to the embodiment of the present invention,the PPP value to be used is not included in the TMGI monitoring responsemessage and may be referenced only upon the transmission of the MBMStraffic later.

Further, if the relay UE 1520 receives the MBMS traffic in step 1730, instep 1740, the relay UE 1520 relays the received MBMS traffic to betransmitted to a PC5 interface using the PPP value.

Next, a method for providing QoS in an EPS network for traffictransmitted through a ProSE UE-network relay will be described.

According to the embodiment of the present invention, the EPS bearer maybe modified or the EPS bearer may generated to provide an appropriateQoS in an EPS network to the remote UE receiving an EPS network servicethrough the ProSe UE-NW relay may be provided.

FIG. 18 is a diagram illustrating an example of a ProSe networkstructure and an EPS and IMS network structure.

Referring to FIG. 18, by the proximity service between the terminals, anIMS service may be received through the EPS network using the ProSeUE-NW relay 1520.

If the ProSe UE-NW relay UE 1520 is within the coverage of the basestation eNB 1530, the ProSe UE-NW relay UE 1520 serves as the relay roleof transferring the service provided from the cellular network 1590 tothe remote UE 1510. Meanwhile, the cellular network 1590 may include thebase station 1530, the ProSe ProSe function 1540, the MME 1550, thegateway (GW) 1560, the HSS 1570, the PCRF 1580, or the like. Further, anIMS network 1810 may include a P-CSCF 1820, an S-CSCF 1830, an MCPTT AS1840, or the like.

Meanwhile, the UE-NW relay UE 1520 may receive various kinds ofinformation for registering that the UE-NW relay UE 1520 is the relayand providing the relay service through the EPS network 1590 or mayprepare the relay service such as the generation of the PDN connectionfor providing the IP service to the remote UE 1510. Further, when therelay service is prepared, the UE-NW relay UE 1520 broadcasts theannouncement message for directly notifying that the UE-NW relay UE 1520is the relay according to the discovery method, such that the remote UE1510 may discover the UE-NW relay UE 1520. Alternatively, the UE-NWrelay UE 1520 receives the discovery solicitation message transmittedwhen the remote UE 1510 therearound finds out the relay, and if meetingthe corresponding condition, the UE-NW relay UE 1520 transmits thediscovery response message and thus the remote UE 1510 may also discoverthe UE-NW relay UE 1520. The remote UE 1510 may select the wanted relayamong the discovered UE-NW relay UEs 1520 to setup the connectionbetween the corresponding UE-NW relay UE 1520 and the remote UE 1510,such that the remote UE 1510 may receive a service through the network.

The remote UE 1510 may receive the MCPTT services such as voicecommunication and image communication through the IMS network 1810 bythe connection. By the way, the allocation of resources to the relay UE1520 in the EPS network 1590 is made between the GW 1560 and the relayUE 1520 and the remote UE 1510 receives a service using the resources.Therefore, a method for providing an appropriate QoS between a GW and arelay UE 1520 is required.

Therefore, to provide the appropriate QoS within the EPS network 1590 tothe remote UE 1510 receiving the EPS network 1590 service through theProSe UE-NW relay 1520, a method for modifying or generating an EPSbearer will be described in detail.

FIG. 19 is a flow chart of allocating an appropriate QoS to an EPSbearer for a relay through a PCRF.

Referring to FIG. 19, according to the embodiment of the presentinvention, the appropriate QoS may be allocated to the EPS bearer forthe purpose of the relay through the PCRF 1580.

For the IMS service, the remote UE 1510 may transmit the SIP message tothe P-CSCF 1820 in step 1910. In this case, the remote UE 1510 sets anaccess type of a P-Access-Network-Info header field of an SIP header as3GPP-EUTRAN-ProSeRelay or 3GPP-EUTRAN-ProSeUNR to notify the P-CSCF 1820that it accesses the IMS network through the ProSe relay. Of course, themethod for notifying the access situation to the IMS network through theProSe relay may also notify the access through the ProSeRelay using aseparate field in addition to the access type. The SIP messagetransmitted from the remote UE 1510 includes SIP registration, SIPinvite, SIP update, SIP 200OK, etc.

Here, for convenience of explanation, the SIP invite message will bedescribed as an example.

In step 1910, if the P-CSCF 1820 receiving the SIP INVITE recognizes theaccess through the ProSe relay, the P-CSCF 1820 may track and find thePCRF 1580 allocating a PCC rule from the source IP address of the IPpacket receiving the SIP invite to the relay UE 1520. Further, theP-CSCF 1820 may transmit an AA request to the found PCRF 1580 in step1930 to transmit information on features of a call flow based on an SDPtransferred along with the SIP message. In this case, the AA requestincludes the IP address of the relay UE 1520 found from the source IPaddress instead of a subscription ID value and a field notifying thatthe AA request is a terminal through the ProSe relay may be inserted. Instep 1935, the PCRF 1580 receiving the AA request tracks and finds outthe IMSI value of the relay UE 1520 based on the corresponding IPaddress. In this case, according to the embodiment of the presentinvention, the PCRF 1580 may also interwork with the PGW 1560 to trackan IMSI value of the relay UE 1520.

As the response thereto, the PCRF 1580 may transfer the AA answer to theP-CSCF 1820 in step 1937. Further, the PCRF 1580 may generate the PCCrule according to the features of the call flow obtained from the AArequest and transfer the generated PCC rule to the PGW 1560. Further,when the PGW 1560 changes the QoS allocated to the existing EPS beareraccording to the PCC rule, in step 1940, the PGW 1560 may transmit theupdate bearer request to the MME 1550. Further, when the PGW 1560generates the separate EPS bearer according to the PCC rule, in step1940, the PGW 1560 may transmit the create bearer request to the MME1550. As a result, the MME 1550 may perform an EPS bearer contextmodification process or a dedicated EPS bearer context activationprocess together with the relay UE 1520 in the steps 1950 and 1960.Further, the MME 1550 may transfer the update bearer response or createbearer response message as the response thereto to the PGW 1560 in thestep 1970. Consequently, the remote UE 1510 transmits data transmittedand received to and from the relay UE 1520 and the ProSe through the EPSnetwork using the modified or generated EPS bearer in step 1980.

According to another embodiment of the present invention, if the P-CSCF1820 receiving the SIP INVITE message recognizes the access through theProSe relay in the step 1910, the P-CSCF 1820 recognizes that it isimpossible to generate the PCC rule for providing the features of thecall flow proposed in the SDP included in the SIP message through the AArequest and thus may also be operated not to perform the AA requestprocess at all. In this case, the PCRF 1580 may not perform the EPSbearer modification or the EPS bearer activation that is triggered.

FIG. 20 is a diagram illustrating a procedure of allowing a remoteterminal to request an appropriate QoS to an EPS bearer for a relay andallocating the QoS to the remote terminal.

Referring to FIG. 20, according to the embodiment of the presentinvention, the remote UE 1510 may directly request the appropriate QoSto the EPS bearer for the purpose of the relay and may be allocated withthe requested QoS.

When transmitting the SIP message for the IMS service, the remote UE1510 sets the access type of the P-Access-Network-Info header field ofthe SIP header as the 3GPP-EUTRAN-ProSeRelay or the 3GPP-EUTRAN-ProSeUNRto notify the state in which the remote UE 1510 accesses the IMS networkthrough the ProSe relay and recognizes that it is impossible to modifyand generate the EPS bearer through the PCRF 1580 as the responsethereto or identically sets the access type with the normal access likethe 3GPP-EUTRAN-FDD or the 3GPP-EUTRAN-TDD without notifying that it isthe IMS access through the ProSe relay using the SIP message, but whenthe fact that it is impossible to modify and generate the EPS bearerthrough the PCRF 1580 is known in advance, may perform the procedure forreceiving the allocation of the appropriate QoS like the presentinvention.

When the remote UE 1510 generates or ends the IMS call, in step 2020,the remote UE 1510 may transfer a resource allocation request message ora resource modification request message to the relay UE 1520 through thePC5 interface. The message may include characteristics of the call flowto be newly added or changed.

In the step 2020, the relay UE 1520 receiving the message may transmit aUE requested bearer resource allocation request message or a UErequested bearer resource modification request message to the MME 1550in step 2030. By doing so, the relay UE 1520 may request the change ofthe QoS through the EPS bearer modification or request the EPS bearergeneration of the new QoS.

Therefore, the MME 1550 may transmit a bearer request command to the PGW1560 in step 2040. Therefore, when the PGW 1560 changes the QoSallocated to the existing EPS bearer or generates the separate EPSbearer according to the PCC rule, in step 2045, the PGW 1560 maytransmit the update bearer request or the create bearer request to theMME 1550. Further, the MME 1550 may perform an EPS bearer contextmodification process or a dedicated EPS bearer context activationprocess together with the relay UE 1520 in step 2050. Further, the MME1550 may transfer the update bearer response or create bearer responsemessage as the response thereto to the PGW 1560 in step 2080. Themodification or generation of the EPS bearer will be described in detailwith reference to the portion associated with FIG. 19.

Further, the relay UE 1520 may transfer a generation result to theremote UE 1510 through the PC5 interface using the resource modificationresponse or resource allocation response message in step 2070.Consequently, the remote UE 1510 transmits data transmitted and receivedto and from the relay UE 1520 and the ProSe through the EPS networkusing the modified or generated EPS bearer in step 2090.

Meanwhile, when the access between the remote UE 1510 and the relay UE1520 is released, the relay UE 1520 requests the UE request bearermodification or transmits the UE request bearer deactivation request tothe MME 1550 as in step 2030 to modify or delete the EPS bearer, therebyeffectively operating the resource.

As another embodiment of the present invention, in FIG. 20, the remoteUE 1510 may not directly perform the resource modification or theresource allocation as in step 2020. Further, by considering the numberof relay UEs 1520 that accesses the relay UE 1520 and the capacity ofthe use traffic, the relay UE 1520 may transmit the UE requested bearerresource allocation request message or the UE requested bearer resourcemodification request message to the MME 1550 in step 2030 to request thechange of the QoS or the generation of the EPS bearer of the new QoSthrough the EPS bearer modification. Therefore, the EPS bearer ismodified or generated by the procedure as in FIG. 20 and then as in thestep 2090, the data transmitted and received between the remote UE 1510and the relay UE 1520 using the ProSe is transmitted through the EPSbearer modified or generated by the process in the EPS network.

Meanwhile, when the access between the remote UE 1510 and the relay UE1520 is released or the use traffic is reduced for a predetermined time,the relay UE 1520 requests the UE request bearer modification ortransmits the UE request bearer deactivation request to the MME 1550 asin step 2030 to modify or delete the EPS bearer, thereby effectivelyoperating the resource.

Next, a method for transferring positional information upon an IMSnetwork through a ProSe UE-network relay will be described.

According to the embodiment of the present invention, to acquire thetracking area code (TAC) and the EUTRAN cell identifier (ECI) includedin the P-access-network-info header field of the SIP message header, theremote UE accessing the MIS network through the ProSe UE-network relayacquires the relevant information through the relay UE or processes theTAC or ECI value as a meaningless value introduces to normally providethe IMS service.

Referring to FIG. 18, the remote UE 1510 may receive the MCPTT servicessuch as the voice communication and the image communication through theIMS network 1810. By the way, when accessing the IMS network 1810through the EPS network 1590, the P-Access-Network-Info header field ofthe SIP header may include the positional information, that is, the MCCand MNC information, the tracking area code (TAC) information, and theEUTRAN cell ID (ECI) information, or the like.

However, the remote UE 1510 does not directly access the eNB 1530 butaccesses the network through the relay UE, thereby removing the TACinformation and the ECI information. Therefore, to normally receive theIMS service, a method for acquiring TAC information and ECI informationis required.

FIG. 21 is a flow chart of providing a dummy value for TAC and ECI to anSIP header.

Referring to FIG. 21, according to the embodiment of the presentinvention, the remote UE 1510 may provide a dummy value for the TAC andthe ECI to the SIP header.

When the remote UE 1510 transmits the SIP message to the P-CSCF1820/S-CSCF 1830 for the IMS service in step 2110, the remote UE 1510sets the access type of the P-Access-Network-Info header field of theSIP header as the 3GPP-EUTRAN-ProSeRelay or the 3GPP-EUTRAN-ProSeUNR tonotify the P-CSCF 1820 that it accesses the IMS network through theProSe relay. For example, it may be put in the header field of the SIPheader as follows.

P-Access-Network-Info: 3GPP-EUTRAN-ProSeRelay;utran-cell-id-3gpp=11122233C476B4321; network-provided orP-Access-Network-Info: 3GPP-EUTRAN-ProSeUNR; utran-cell-id-3gpp=11122233C476B4321; network-provided.

The first six digits 111222 represent PLMN information, the next fourdigits 33C4 represent TAC information, and the next seven digits 76B4321represent ECI information.

Of course, the method for notifying an access to an IMS network througha ProSe relay may also notify the access through the ProSe Relay usingthe separate field in addition to the access type. The SIP messagetransferred from the remote UE 1510 includes SIP registration, SIPinvite, SIP update, SIP 200OK, etc.

Here, for convenience of explanation, the SIP registration message willbe described as an example.

In this case, if the IMS entities such as the P-CSCF 1820 or the S-CSCF1830 that receive the SIP registration message recognize the accessthrough the ProSe relay from the header information, the IMS entitiesmay consider the TAC information value (33C4 in the drawing) and the ECIinformation value (76B4321 in the drawing) included in theP-Access-Network-Info header field as a dummy value and disregard therelated value.

FIG. 22 is another flow chart of providing the dummy value for the TACand the ECI to the SIP header.

Referring to FIG. 22, according to the embodiment of the presentinvention, the remote UE 1510 may provide the dummy value for the TACand the ECI to the SIP header.

When the remote UE 1510 transmits the SIP message to the P-CSCF1820/S-CSCF 1830 for the IMS service in step 2210, the remote UE 1510sets the access type of the P-Access-Network-Info header field of theSIP header as a 3GPP-EUTRAN-TDD or a 3GPP-EUTRAN-FDD by the same methodas the SIP message through the general EPS network. However, it may benotified that the dummy value is used, by using the pre-defined TAC orpre-defined ECI value previously engaged between the provider and theterminal. For example, the pre-defined TAC=FFF and the pre-defined ECImay be put in the header field as follows.

When the remote UE 1510 does not know only the TAC value, the headerfield may be as follows.

P-Access-Network-Info: 3GPP-EUTRAN-ProSeFDD;utran-cell-id-3gpp=111222FFFF76B4321; network-provided.

When the remote UE 1510 does not know both of the TAC value and the ECIvalue, the header field may be as follows.

P-Access-Network-Info: 3GPP-EUTRAN-ProSeFDD;utran-cell-id-3gpp=111222FFFFFFFFFFF; network-provided.

The SIP message transmitted from the remote UE 1510 includes SIPregistration, SIP invite, SIP update, SIP 200OK, etc.

Here, for convenience of explanation, the SIP registration message willbe described as an example.

If the IMS entities such as the P-CSCF 1820 or the S-CSCF 1830 receivingthe SIP registration message recognize from the header information thatthe dummy value is used in step 2220, the corresponding TAC and ECIvalue included in the P-Access-Network-info header field may bedisregarded.

FIG. 23 is a flow chart illustrating an example of a procedure ofallowing a remote UE to request a relay UE to acquire ECGI and TACvalues.

Referring to FIG. 23, according to the embodiment of the presentinvention, the remote UE 1510 may request the relay UE 1520 to acquirethe ECGI and TAC values.

In step 2310, the remote UE 1510 may transmit a cell ID announcementrequest message to the relay UE 1520 to request the cell information. Instep 2320, the relay UE 1520 may transmit a refresh timer to the remoteUE 1510 along with the cell ID announcement response. Further, in step2330, when the corresponding refresh timer expires, the relay UE 1520may broadcast the cell ID announcement. The cell ID announcement messageincludes the ECGI information as well as the TAC information of the cellthat the relay UE 1520 accesses. Therefore, the remote UE 1510 receivingthe cell ID announcement message may acquire the PLMN information andthe ECI information from the ECGI information of the relay UE receivedfrom the relay UE 1520 and use the TAC information of the relay UE 1520received simultaneously therewith to reflect it to the SIP messageheader. For example, it may be put in the header field as follows.

P-Access-Network-Info: 3GPP-EUTRAN-FDD;utran-cell-id-3gpp=11122233C476B4321; network-provided.

The first six digits 111222 represent PLMN information, the next fourdigits 33C4 represent TAC information, and the next seven digits 76B4321represent ECI information. Further, in step 2340, the remote UE 1510 maytransmit the SIP message to the IMS entities such as the P-CSCF 1820 orthe S-CSCF 1830.

FIG. 24 is a flow chart illustrating another example of the procedure ofallowing a remote UE to request a relay UE to acquire ECGI and TACvalues.

Referring to FIG. 24, according to the embodiment of the presentinvention, the remote UE 1510 may request the relay UE 1520 to acquirethe ECGI and TAC values.

In step 2410, the remote UE 1510 may transmit the cell ID announcementrequest message to the relay UE 1520 to request the cell informationwhenever it transmits the SIP message. Further, in step 2420, the relayUE 1520 may transmit the cell information response including the ECGIand TAC information of the relay UE 1510.

Therefore, the remote UE 1510 receiving the cell information responsemay acquire the PLMN information and the ECI information from the ECGIinformation of the relay UE received from the relay UE 1520 and use theTAC information of the relay UE 1520 received simultaneously therewithto reflect it to the SIP message header. For example, it may be put inthe header field as follows.

P-Access-Network-Info: 3GPP-EUTRAN-FDD;utran-cell-id-3gpp=11122233C476B4321; network-provided.

The first six digits 111222 represent PLMN information, the next fourdigits 33C4 represent TAC information, and the next seven digits 76B4321represent ECI information. Further, in step 2430, the remote UE 1510 maytransmit the SIP message to the IMS entities such as the P-CSCF 1820 orthe S-CSCF 1830.

FIG. 25 is a block configuration diagram of a terminal according to anembodiment of the present invention.

Referring to FIG. 25, the terminal according to one embodiment of thepresent invention may include a transceiver 2510 and a controller 2520controlling the overall operation of the terminal. In this case, theterminal may mean any one of an MCPTT terminal, a CloT terminal, an LTEand CloT terminal, a remote terminal, and a relay terminal.

The controller 2520 of the terminal controls the terminal to perform anyone operation of the foregoing embodiments. For example, when theterminal is the remote terminal, the controller 2520 of the terminal mayperform a control to transmit the TMGI monitoring request messageincluding the Prose per packet priority to the relay terminal andreceive the MBMS traffic from the relay terminal depending on the ProSeper packet priority. Alternatively, when the terminal is the relayterminal, the controller 2520 of the terminal may perform a control toreceive the TMGI monitoring request message including the Prose perpacket priority from the remote terminal and transmit the MBMS trafficto the remote terminal depending on the ProSe per packet priority.

Further, the transceiver 2510 of the terminal may transmit and receive asignal according to any one operation of the foregoing embodiments. Forexample, when the terminal is the remote terminal, the transceiver 2510of the terminal may transmit the TMGI monitoring request messageincluding the ProSe per packet priority to the relay terminal andreceive the MBMS traffic. Further, when the terminal is the relayterminal, the transceiver 2510 of the terminal may receive the TMGImonitoring request message including the ProSe per packet priority fromthe remote terminal and transmit the MBMS traffic.

FIG. 26 is a block configuration diagram of network entity according toan embodiment of the present invention.

Referring to FIG. 25, the network entity according to one embodiment ofthe present invention may include a transceiver 2610 and a controller2620 controlling the overall operation of the terminal. In this case, aslong as the network entity is network entities for describing theembodiment of the present invention such as the base station, the MME,the PreSe function, the MCPTT application server, the P-CSCF, the HSS,the GW, the MSSC, and the MCE, any network entity may correspondthereto.

The controller 2620 of the network entity controls the network entity toperform any one operation of the foregoing embodiments. For example,when the network entity is the GCS AS, the controller 2620 of thenetwork entity may perform a control to receive the ECGI list from theterminal. Alternatively, when the network entity is the ProSe function,the controller 2620 of the network entity may perform a control toreceive the service authorization request message from the remoteterminal.

Further, the transceiver 2610 of the network entity may transmit andreceive a signal according to any one operation of the foregoingembodiments. For example, when the network entity is the GCS AS, thetransceiver 2610 of the network entity may receive the ECGI list fromthe terminal. Alternatively, when the network entity is the ProSefunction, the transceiver 2610 of the network entity may receive theservice authorization request message from the remote terminal.

The embodiments of the present invention disclosed in the presentspecification and the accompanying drawings have been provided to easilydescribe and assist in understanding the described content and do notlimit the scope of the present invention. It is obvious to those skilledin the art to which the present invention pertains that variousmodifications may be made without departing from the scope of thepresent invention, in addition to the embodiments disclosed herein.

Meanwhile, although the exemplary embodiments of the present inventionhave been illustrated in the present specification and the accompanyingdrawings and specific terms have been used, they are used in a generalmeaning in order to assist in the understanding the present inventionand do not limit the scope of the present invention. It is obvious tothose skilled in the art to which the present invention pertains thatvarious modifications may be made without departing from the scope ofthe present invention, in addition to the exemplary embodimentsdisclosed herein.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method of a proxy call session control function(P-CSCF) in a wireless communication system, the method comprising:receiving, from a remote terminal, a first message including firstinformation indicating that the remote terminal accesses through a relayterminal; determining a policy and charging rules function (PCRF)serving a relay connection of the relay terminal; and transmitting, tothe PCRF, a second message including second information on a servicerelated to the remote terminal for requesting the PCRF to validate theservice.
 2. The method of claim 1, wherein the determining the PCRFcomprises: determining the PCRF based on a source internet protocol (IP)address of the remote terminal.
 3. The method of claim 1, wherein thefirst message includes a session initiation protocol (SIP) message. 4.The method of claim 1, wherein the first information includes an accesstype field set to 3GPP-E-UTRAN-ProSe-UNR.
 5. The method of claim 1,wherein the first message further includes a utran-cell-id-3gppparameter including public land mobile network (PLMN) information andE-UTRAN cell identity (ECI).
 6. A method of a policy and charging rulesfunction (PCRF) in a wireless communication system, the methodcomprising: receiving, from a proxy call session control function(P-CSCF), a first message including first information on a servicerelated to a remote terminal, in a case that the P-CSCF receives asecond message including second information indicating that a remoteterminal accesses through a relay terminal; and validating the servicerelated to the remote terminal based on a relay functionality.
 7. Themethod of claim 6, wherein the PCRF is determined based on a sourceinternet protocol (IP) address of the remote terminal by the P-CSCF. 8.The method of claim 6, wherein the second message includes a sessioninitiation protocol (SIP) message.
 9. The method of claim 6, wherein thesecond information includes an access type field set to3GPP-E-UTRAN-ProSe-UNR.
 10. The method of claim 6, wherein the secondmessage further includes a utran-cell-id-3gpp parameter including publicland mobile network (PLMN) information and E-UTRAN cell identity (ECI).11. A proxy call session control function (P-CSCF) comprising: atransceiver; and a controller coupled with the transceiver andconfigured to: receive, from a remote terminal, a first messageincluding first information indicating that the remote terminal accessesthrough a relay terminal; determine a policy and charging rules function(PCRF) serving a relay connection of the relay terminal; and transmit,to the PCRF, a second message including second information on a servicerelated to the remote terminal for requesting the PCRF to validate theservice.
 12. The P-CSCF of claim 11, wherein the controller isconfigured to determine the PCRF based on a source internet protocol(IP) address of the remote terminal.
 13. The P-CSCF of claim 11, whereinthe first message includes a session initiation protocol (SIP) message.14. The P-CSCF of claim 11, wherein the first information includes anaccess type field set to 3GPP-E-UTRAN-ProSe-UNR.
 15. The P-CSCF of claim11, wherein the first message further includes a utran-cell-id-3gppparameter including public land mobile network (PLMN) information andE-UTRAN cell identity (ECI).
 16. A policy and charging rules function(PCRF) comprising: a transceiver; and a controller coupled with thetransceiver and configured to: receive, from a proxy call sessioncontrol function (P-CSCF), a first message including first informationon a service related to a remote terminal, in a case that the P-CSCFreceives a second message including second information indicating that aremote terminal accesses through a relay terminal; and validate theservice related to the remote terminal based on a relay functionality.17. The PCRF of claim 16, wherein the PCRF is determined based on asource internet protocol (IP) address of the remote terminal by theP-CSCF.
 18. The PCRF of claim 16, wherein the second message includes asession initiation protocol (SIP) message.
 19. The PCRF of claim 6,wherein the second information includes an access type field set to3GPP-E-UTRAN-ProSe-UNR.
 20. The PCRF of claim 16, wherein the secondmessage further includes a utran-cell-id-3gpp parameter including publicland mobile network (PLMN) information and E-UTRAN cell identity (ECI).